Rebuild after release - fix #3118 #3120
Open
+3
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
wget https://registry.npmjs.org/@redis/client/-/client-5.9.0.tgz
mkdir client-5.9.0
tar -xzvf client-5.9.0.tgz -C client-5.9.0
grep "version" client-5.9.0/package.json # "version": "5.9.0",
but inside the dist/
grep "version" client-5.9.0/dist/package.json # "version": "5.9.0-beta
The release workflow has a timing issue where:
The build process (npm run build) runs before the version bump
This creates the dist/package.json with the beta version (5.9.0-beta.3)
Then release-it updates the source package.json to the final version (5.9.0)
But the dist/package.json is never updated, so it still contains the beta version
The Solution:
The release workflow needs to rebuild the packages after the version bump but before publishing to npm.
Checklist
npm testpass with this change (including linting)?